Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 450988e0e247ef849a12932325f5f94b59e14b8c2f258f4ca8179aa147c40c0f

Tx prefix hash: 4f6ea1ba7408cc26680fe7f337d610ea7a0fe44e647ab1970b3cd61c4041747e
Tx public key: 63478a8a9fc7729aa469b1f78a836de9a889fa77b0f37786d7d685d82269c52f
Timestamp: 1750944210 Timestamp [UCT]: 2025-06-26 13:23:30 Age [y:d:h:m:s]: 00:142:15:03:26
Block: 1313208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99931 RingCT/type: yes/0
Extra: 0163478a8a9fc7729aa469b1f78a836de9a889fa77b0f37786d7d685d82269c52f02110000000643846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0d2d1d032d2a77ea5dd7362376f7b8a60004fbbf00b57a163164f76ef22c8f9 0.600000000000 1800847 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": 1313218, "vin": [ { "gen": { "height": 1313208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0d2d1d032d2a77ea5dd7362376f7b8a60004fbbf00b57a163164f76ef22c8f9" } } ], "extra": [ 1, 99, 71, 138, 138, 159, 199, 114, 154, 164, 105, 177, 247, 138, 131, 109, 233, 168, 137, 250, 119, 176, 243, 119, 134, 215, 214, 133, 216, 34, 105, 197, 47, 2, 17, 0, 0, 0, 6, 67, 132, 109, 102, 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