Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1eddd9a519d6e42e1e6e4896ef7aa42a1a9d10f175fbe759c1d3d3272b9e2b1c

Tx prefix hash: fda949ce3eb6331573c711e76361d6d69c4f0ed97e2b560d73e5f8fd9a4aae2d
Tx public key: b046b98c192fea1c6cb2d7191d144ef1e285028e87b16d6617e5eeb0946425e1
Timestamp: 1759256560 Timestamp [UCT]: 2025-09-30 18:22:40 Age [y:d:h:m:s]: 00:090:12:55:22
Block: 1379887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64833 RingCT/type: yes/0
Extra: 01b046b98c192fea1c6cb2d7191d144ef1e285028e87b16d6617e5eeb0946425e102110000000197baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d212a0750214b048a9418e77e197876955407c977cd1533e14448b3db26c52c1 0.600000000000 1867998 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": 1379897, "vin": [ { "gen": { "height": 1379887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d212a0750214b048a9418e77e197876955407c977cd1533e14448b3db26c52c1" } } ], "extra": [ 1, 176, 70, 185, 140, 25, 47, 234, 28, 108, 178, 215, 25, 29, 20, 78, 241, 226, 133, 2, 142, 135, 177, 109, 102, 23, 229, 238, 176, 148, 100, 37, 225, 2, 17, 0, 0, 0, 1, 151, 186, 249, 34, 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