Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 071a2d8e649a32cb0fe290c129245ff89f911e21e57660fa635cfec6ca142579

Tx prefix hash: 64dc5163d253f5dc83ea6051112cc7cb5332f8ee4f74583a3f2f97992201f5ad
Tx public key: 73d024c04f9bbe74c61f2ce27846d901cf9db11a74ab7440a6770d66c2ae7fab
Timestamp: 1747336954 Timestamp [UCT]: 2025-05-15 19:22:34 Age [y:d:h:m:s]: 00:188:13:00:29
Block: 1283654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132460 RingCT/type: yes/0
Extra: 0173d024c04f9bbe74c61f2ce27846d901cf9db11a74ab7440a6770d66c2ae7fab0211000000049f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a40aa4d882971b4d7010a3fc238b076022e6e6b4600b071c8a5b4a2780b3da56 0.600000000000 1771073 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": 1283664, "vin": [ { "gen": { "height": 1283654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a40aa4d882971b4d7010a3fc238b076022e6e6b4600b071c8a5b4a2780b3da56" } } ], "extra": [ 1, 115, 208, 36, 192, 79, 155, 190, 116, 198, 31, 44, 226, 120, 70, 217, 1, 207, 157, 177, 26, 116, 171, 116, 64, 166, 119, 13, 102, 194, 174, 127, 171, 2, 17, 0, 0, 0, 4, 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