Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c55f8b4716df776cd2d781b8fedab604af3f801e93540a54a0cc56a4c18574ae

Tx prefix hash: b506977beee71d84584398d53acb979553fee9f98e4d4913c451f703eb0b4e93
Tx public key: 1a0e8aeac408756aa8af453ebb8530e038fc19f01bfa75f613b53a182a2bf96b
Timestamp: 1733660186 Timestamp [UCT]: 2024-12-08 12:16:26 Age [y:d:h:m:s]: 00:100:22:44:48
Block: 1170710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71950 RingCT/type: yes/0
Extra: 011a0e8aeac408756aa8af453ebb8530e038fc19f01bfa75f613b53a182a2bf96b021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77b1464c7c2d8e75258bf2845de219a31ad12fd038aca50962eb393294ccd3b4 0.600000000000 1656443 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": 1170720, "vin": [ { "gen": { "height": 1170710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77b1464c7c2d8e75258bf2845de219a31ad12fd038aca50962eb393294ccd3b4" } } ], "extra": [ 1, 26, 14, 138, 234, 196, 8, 117, 106, 168, 175, 69, 62, 187, 133, 48, 224, 56, 252, 25, 240, 27, 250, 117, 246, 19, 181, 58, 24, 42, 43, 249, 107, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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