Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 346d8c222ef41c760b0e4c57945cdff82e9d35bd80abac6a5c1470e80cf46529

Tx prefix hash: d5a84a2b157db4144979fe2f009f388035bc97fc328139307c24b9afb808f0a2
Tx public key: cab8f5598d1f6c09435afd3580e9e1131ffd43161f7ab7dcfed9f6bf5a8a8fbe
Timestamp: 1739863605 Timestamp [UCT]: 2025-02-18 07:26:45 Age [y:d:h:m:s]: 00:255:17:25:48
Block: 1221753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180545 RingCT/type: yes/0
Extra: 01cab8f5598d1f6c09435afd3580e9e1131ffd43161f7ab7dcfed9f6bf5a8a8fbe02110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f87e38c78f98f9742341d6f21ac955ee86751f2e058508d326a7fe899caac042 0.600000000000 1708600 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1221763, "vin": [ { "gen": { "height": 1221753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f87e38c78f98f9742341d6f21ac955ee86751f2e058508d326a7fe899caac042" } } ], "extra": [ 1, 202, 184, 245, 89, 141, 31, 108, 9, 67, 90, 253, 53, 128, 233, 225, 19, 31, 253, 67, 22, 31, 122, 183, 220, 254, 217, 246, 191, 90, 138, 143, 190, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8