Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dcf0921924551fbce8b459d379ed519f06aaed5abeec2f3fcceb0dd0d5f9cf2

Tx prefix hash: cee40056c6b9ffe44876795e56046a5aa38c69154c2719f2916f7a419db57865
Tx public key: a14d853725b60b330fb0fb2cb067ba0fb13e9242c622d6f287356d6a249bbfcb
Timestamp: 1707736957 Timestamp [UCT]: 2024-02-12 11:22:37 Age [y:d:h:m:s]: 01:085:23:37:00
Block: 955884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322519 RingCT/type: yes/0
Extra: 01a14d853725b60b330fb0fb2cb067ba0fb13e9242c622d6f287356d6a249bbfcb02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc26e174c1d7ca88071c4367734bf9a137943583bf30389014141f16d8b145f6 0.600000000000 1415184 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": 955894, "vin": [ { "gen": { "height": 955884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc26e174c1d7ca88071c4367734bf9a137943583bf30389014141f16d8b145f6" } } ], "extra": [ 1, 161, 77, 133, 55, 37, 182, 11, 51, 15, 176, 251, 44, 176, 103, 186, 15, 177, 62, 146, 66, 198, 34, 214, 242, 135, 53, 109, 106, 36, 155, 191, 203, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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