Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e29280e5a0de17e4de17e6d4d1b20721e1992171cf3185c996aa4460037fa0e4

Tx prefix hash: 128326ab9eb4d4ae5e5ff6344118ef679be2c8bb1a00d51dc5c41edb853d503a
Tx public key: 9cfaa1cda6573a3da13b71b7f9dcae655c442430eb06186acc77a3d2aec61e36
Timestamp: 1749499845 Timestamp [UCT]: 2025-06-09 20:10:45 Age [y:d:h:m:s]: 00:154:01:27:54
Block: 1301575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107776 RingCT/type: yes/0
Extra: 019cfaa1cda6573a3da13b71b7f9dcae655c442430eb06186acc77a3d2aec61e3602110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 002a1289c6cc905343dddd102eb510d57f3db96135c2e70eff9bfe6ae05518c8 0.600000000000 1789134 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": 1301585, "vin": [ { "gen": { "height": 1301575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "002a1289c6cc905343dddd102eb510d57f3db96135c2e70eff9bfe6ae05518c8" } } ], "extra": [ 1, 156, 250, 161, 205, 166, 87, 58, 61, 161, 59, 113, 183, 249, 220, 174, 101, 92, 68, 36, 48, 235, 6, 24, 106, 204, 119, 163, 210, 174, 198, 30, 54, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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