Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c78e0eda28e92afcfda9ec194bc396551236d3cc184991fe0ce12dc0d607b1fe

Tx prefix hash: 936f1d448bcf74d04cb86fc088bcfd022e3424a1f2d6a1d171b745cae76fb929
Tx public key: 99471d5a7045449e11f25226e81055139a1e7e02fab99cbdbd2bf504e5e1f121
Timestamp: 1761002684 Timestamp [UCT]: 2025-10-20 23:24:44 Age [y:d:h:m:s]: 00:037:21:39:52
Block: 1394393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27124 RingCT/type: yes/0
Extra: 0199471d5a7045449e11f25226e81055139a1e7e02fab99cbdbd2bf504e5e1f121021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87920417fc4e82ba2d4e5672b71fddd6509d3d52e2f65a2a38b44e8a715b2187 0.600000000000 1882664 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": 1394403, "vin": [ { "gen": { "height": 1394393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87920417fc4e82ba2d4e5672b71fddd6509d3d52e2f65a2a38b44e8a715b2187" } } ], "extra": [ 1, 153, 71, 29, 90, 112, 69, 68, 158, 17, 242, 82, 38, 232, 16, 85, 19, 154, 30, 126, 2, 250, 185, 156, 189, 189, 43, 245, 4, 229, 225, 241, 33, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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