Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e16f2ec9806f095f3124b28acf2b39576dcbc8e8f4a1cb74a4b8bb8087ffaae

Tx prefix hash: a9ddd12f03c8156376501206b9fbf2ad06e893a51e29eff575473de0bc846f23
Tx public key: 4d81ab8d779b8e2920248b42feab4b56600599fd27e27f5db1649953d7059e01
Timestamp: 1745927311 Timestamp [UCT]: 2025-04-29 11:48:31 Age [y:d:h:m:s]: 00:011:21:18:39
Block: 1272001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8494 RingCT/type: yes/0
Extra: 014d81ab8d779b8e2920248b42feab4b56600599fd27e27f5db1649953d7059e010211000000079f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f79f1c6060f9f60eae1f55b74a5133af5f8f78fd7cd46a5edab94a1d96d6e66 0.600000000000 1759272 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": 1272011, "vin": [ { "gen": { "height": 1272001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f79f1c6060f9f60eae1f55b74a5133af5f8f78fd7cd46a5edab94a1d96d6e66" } } ], "extra": [ 1, 77, 129, 171, 141, 119, 155, 142, 41, 32, 36, 139, 66, 254, 171, 75, 86, 96, 5, 153, 253, 39, 226, 127, 93, 177, 100, 153, 83, 215, 5, 158, 1, 2, 17, 0, 0, 0, 7, 159, 159, 230, 140, 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