Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f068e9df3f97bfb26bf3bc6c1c5a56ee95e3bfabbeeafc0256ba291f67bf564

Tx prefix hash: f7dfff2eff98e96193472477a50a38379416da21f3d5ff3426758a200adeb2f4
Tx public key: 7340aef434e118617432144f2bc51ed614f002819ea8c866015e6abaf70b2a20
Timestamp: 1650369807 Timestamp [UCT]: 2022-04-19 12:03:27 Age [y:d:h:m:s]: 03:027:02:28:22
Block: 483538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 799980 RingCT/type: yes/0
Extra: 017340aef434e118617432144f2bc51ed614f002819ea8c866015e6abaf70b2a20021100000001cb8520c2000000000000000000

1 output(s) for total of 15.340450352000 dcy

stealth address amount amount idx
00: e0982b2f6df7b3bcd886e4e2cfde3afc9b2e56ba7268b252d7fa5c20b37b9cd4 15.340450352000 905241 of 0

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": 483548, "vin": [ { "gen": { "height": 483538 } } ], "vout": [ { "amount": 15340450352, "target": { "key": "e0982b2f6df7b3bcd886e4e2cfde3afc9b2e56ba7268b252d7fa5c20b37b9cd4" } } ], "extra": [ 1, 115, 64, 174, 244, 52, 225, 24, 97, 116, 50, 20, 79, 43, 197, 30, 214, 20, 240, 2, 129, 158, 168, 200, 102, 1, 94, 106, 186, 247, 11, 42, 32, 2, 17, 0, 0, 0, 1, 203, 133, 32, 194, 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