Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2724a1c5bb0741cc1c05359dfe9e927ff70de6fff75a9077be9c3bcd2e99aa3

Tx prefix hash: fb0f513059f7f900e91204239753785313c24e3103d0140c2818577ed92fb22c
Tx public key: 58485b805e71754f794fe232b90a86b4fe2f527fb043e5a761367e75f5f1864b
Timestamp: 1578394215 Timestamp [UCT]: 2020-01-07 10:50:15 Age [y:d:h:m:s]: 04:304:15:57:31
Block: 40409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1107100 RingCT/type: yes/0
Extra: 0158485b805e71754f794fe232b90a86b4fe2f527fb043e5a761367e75f5f1864b021100000002dcee4b4d000000000000000000

1 output(s) for total of 450.937703103000 dcy

stealth address amount amount idx
00: d007b041675045c941560e18f9308e45746f0b0be03edb7bec1075a7293305c1 450.937703103000 70904 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": 40419, "vin": [ { "gen": { "height": 40409 } } ], "vout": [ { "amount": 450937703103, "target": { "key": "d007b041675045c941560e18f9308e45746f0b0be03edb7bec1075a7293305c1" } } ], "extra": [ 1, 88, 72, 91, 128, 94, 113, 117, 79, 121, 79, 226, 50, 185, 10, 134, 180, 254, 47, 82, 127, 176, 67, 229, 167, 97, 54, 126, 117, 245, 241, 134, 75, 2, 17, 0, 0, 0, 2, 220, 238, 75, 77, 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