Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b2394160c23152a1377160c3340617a2e1ffbc6e859def080781e7c1c02bc6b

Tx prefix hash: 51c12f9cb69ce02bc392d21eb9fbad157b0dde444212fb739a5d924dca2b9534
Tx public key: 6231415d49921e8c787732a537423b4bad736995549c39f99fd3556e8aa127f3
Timestamp: 1578992707 Timestamp [UCT]: 2020-01-14 09:05:07 Age [y:d:h:m:s]: 05:092:23:34:04
Block: 45207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1216672 RingCT/type: yes/0
Extra: 016231415d49921e8c787732a537423b4bad736995549c39f99fd3556e8aa127f302110000000a4ac5aa02000000000000000000

1 output(s) for total of 434.721663244000 dcy

stealth address amount amount idx
00: e90bf724c5007baa075a6a69cb6fe5a87430d54c691177245e4bdcfa11e40119 434.721663244000 82521 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": 45217, "vin": [ { "gen": { "height": 45207 } } ], "vout": [ { "amount": 434721663244, "target": { "key": "e90bf724c5007baa075a6a69cb6fe5a87430d54c691177245e4bdcfa11e40119" } } ], "extra": [ 1, 98, 49, 65, 93, 73, 146, 30, 140, 120, 119, 50, 165, 55, 66, 59, 75, 173, 115, 105, 149, 84, 156, 57, 249, 159, 211, 85, 110, 138, 161, 39, 243, 2, 17, 0, 0, 0, 10, 74, 197, 170, 2, 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