Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b22a3fe9d256e673c3d98858b379dbac9738c20ddb4a580c1cb9aea71583c6f

Tx prefix hash: aa874e1273c48d39f80a021db931964b657776ee754a4b40f8bc60552386f465
Tx public key: aea1e62a170d4a57b94c260fe615cdc3ff9b9d0a80f7465ee6031b5618166a60
Timestamp: 1726430136 Timestamp [UCT]: 2024-09-15 19:55:36 Age [y:d:h:m:s]: 00:226:01:10:53
Block: 1110861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161413 RingCT/type: yes/0
Extra: 01aea1e62a170d4a57b94c260fe615cdc3ff9b9d0a80f7465ee6031b5618166a60021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91903225961d43f2764e7648b286a215663dc1fba6f12390a346ed11d34d4807 0.600000000000 1589622 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": 1110871, "vin": [ { "gen": { "height": 1110861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91903225961d43f2764e7648b286a215663dc1fba6f12390a346ed11d34d4807" } } ], "extra": [ 1, 174, 161, 230, 42, 23, 13, 74, 87, 185, 76, 38, 15, 230, 21, 205, 195, 255, 155, 157, 10, 128, 247, 70, 94, 230, 3, 27, 86, 24, 22, 106, 96, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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