Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 980e07e160f1c1b94abfb16005200b48d5bba5d6df01505a35349082a7929da4

Tx prefix hash: dcd0affbaf3795763896947b8c325f00d572f797767a622b591daf45a5dcac87
Tx public key: 2dfa1ba3cfd7910da72531ebf8de32011ea55c6e5be478b08f51322c7f7810bf
Timestamp: 1582252264 Timestamp [UCT]: 2020-02-21 02:31:04 Age [y:d:h:m:s]: 04:270:15:21:38
Block: 69217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1085899 RingCT/type: yes/0
Extra: 012dfa1ba3cfd7910da72531ebf8de32011ea55c6e5be478b08f51322c7f7810bf02110000000256c366d3000000000000000000

1 output(s) for total of 361.962558648000 dcy

stealth address amount amount idx
00: ff1e0fe2e19477918209ffd89b487938ad98a94e6b6da7ff4d4ef18a032377c3 361.962558648000 127619 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": 69227, "vin": [ { "gen": { "height": 69217 } } ], "vout": [ { "amount": 361962558648, "target": { "key": "ff1e0fe2e19477918209ffd89b487938ad98a94e6b6da7ff4d4ef18a032377c3" } } ], "extra": [ 1, 45, 250, 27, 163, 207, 215, 145, 13, 167, 37, 49, 235, 248, 222, 50, 1, 30, 165, 92, 110, 91, 228, 120, 176, 143, 81, 50, 44, 127, 120, 16, 191, 2, 17, 0, 0, 0, 2, 86, 195, 102, 211, 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