Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c90d999b2b5cf24d174afa420219d13a4d706a4fc8e079dc65fed2341c2d828

Tx prefix hash: 4bc96b432b98ec81dc30dea095b40feb83f4ca35101de3c05565dc0f29a05d21
Tx public key: 7c25a58c2811517010c87d1b798619edb92e2d708e33dcd054fe4ad2a402762c
Timestamp: 1714253166 Timestamp [UCT]: 2024-04-27 21:26:06 Age [y:d:h:m:s]: 01:189:23:42:40
Block: 1009910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394407 RingCT/type: yes/0
Extra: 017c25a58c2811517010c87d1b798619edb92e2d708e33dcd054fe4ad2a402762c0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe1284faa741c9a3d244bc65563b174afe02a120a364f610db0199ea24ad8bd8 0.600000000000 1471716 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": 1009920, "vin": [ { "gen": { "height": 1009910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe1284faa741c9a3d244bc65563b174afe02a120a364f610db0199ea24ad8bd8" } } ], "extra": [ 1, 124, 37, 165, 140, 40, 17, 81, 112, 16, 200, 125, 27, 121, 134, 25, 237, 185, 46, 45, 112, 142, 51, 220, 208, 84, 254, 74, 210, 164, 2, 118, 44, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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