Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b08ff1e9a2931ceb0aa04f2441eb6e1d8d21618cce665b16a0ab71be9ca5bd6

Tx prefix hash: 8a5266d0fb407d22fd45d8ad8ee3b5c7181a9755d1b576c2291a75d5d7a1fc21
Tx public key: 88fb33b497ca34e5bc8d29e95f3d235c372c36417411283b6731423d1644029b
Timestamp: 1736028393 Timestamp [UCT]: 2025-01-04 22:06:33 Age [y:d:h:m:s]: 00:101:11:25:44
Block: 1190310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72306 RingCT/type: yes/0
Extra: 0188fb33b497ca34e5bc8d29e95f3d235c372c36417411283b6731423d1644029b021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9026dbc3c165c51843a06ec34518dcabda26dae8f75be51ee517ee3e0bd97f46 0.600000000000 1676825 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": 1190320, "vin": [ { "gen": { "height": 1190310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9026dbc3c165c51843a06ec34518dcabda26dae8f75be51ee517ee3e0bd97f46" } } ], "extra": [ 1, 136, 251, 51, 180, 151, 202, 52, 229, 188, 141, 41, 233, 95, 61, 35, 92, 55, 44, 54, 65, 116, 17, 40, 59, 103, 49, 66, 61, 22, 68, 2, 155, 2, 17, 0, 0, 0, 4, 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