Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9b21709e8087cb415a1da8801e950d8e781de76f1e07ae7e5178bd83b792b21

Tx prefix hash: 3fc4bc0d38e47d3a3b9ffbce0025511e4ff0ba9470c8b05d226e680f2a4b6dd8
Tx public key: 59b612428fe7a3c9620a27a0a1e56cc98250d747b482b165304d606e769780fc
Timestamp: 1718353374 Timestamp [UCT]: 2024-06-14 08:22:54 Age [y:d:h:m:s]: 00:300:01:40:56
Block: 1043911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214435 RingCT/type: yes/0
Extra: 0159b612428fe7a3c9620a27a0a1e56cc98250d747b482b165304d606e769780fc0211000000048fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b0f2feb47a502257a215a80c5ff3a1e63c33ca3cee771d723e46446827dbbcd 0.600000000000 1513074 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": 1043921, "vin": [ { "gen": { "height": 1043911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b0f2feb47a502257a215a80c5ff3a1e63c33ca3cee771d723e46446827dbbcd" } } ], "extra": [ 1, 89, 182, 18, 66, 143, 231, 163, 201, 98, 10, 39, 160, 161, 229, 108, 201, 130, 80, 215, 71, 180, 130, 177, 101, 48, 77, 96, 110, 118, 151, 128, 252, 2, 17, 0, 0, 0, 4, 143, 218, 155, 45, 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