Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40e7a1274351e94ee931f5639ca038202b6eec3e7185532ae48bd80971be769d

Tx prefix hash: 21d16bdad6059c6b2369645147238c0902eec45385d1dcc46fe9037ca2b2368e
Tx public key: 84dd630aa70e55db8a2fb560e2e8c8b2a7b3a12169afe513ae3906db785ef6a0
Timestamp: 1720144293 Timestamp [UCT]: 2024-07-05 01:51:33 Age [y:d:h:m:s]: 00:279:04:21:04
Block: 1058746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199482 RingCT/type: yes/0
Extra: 0184dd630aa70e55db8a2fb560e2e8c8b2a7b3a12169afe513ae3906db785ef6a00211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa100d16b887e81ebf179ebd23a2cea0437433fe0f36d82f8a90aeb9543331f2 0.600000000000 1529203 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": 1058756, "vin": [ { "gen": { "height": 1058746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa100d16b887e81ebf179ebd23a2cea0437433fe0f36d82f8a90aeb9543331f2" } } ], "extra": [ 1, 132, 221, 99, 10, 167, 14, 85, 219, 138, 47, 181, 96, 226, 232, 200, 178, 167, 179, 161, 33, 105, 175, 229, 19, 174, 57, 6, 219, 120, 94, 246, 160, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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