Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89f114c1042d2587f3097762329e1a80def8df73d94c27f193b71ec9e23dafb4

Tx prefix hash: 45cad0c63cc05ba09dbd47e4336da14194f82ed1d3aa42d3f528e59ad2adfb99
Tx public key: 417d46a0b8559577c5c8e01499b52be821c5e1cda41007ae663ca076a1611d80
Timestamp: 1577753729 Timestamp [UCT]: 2019-12-31 00:55:29 Age [y:d:h:m:s]: 05:064:22:52:34
Block: 35400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196177 RingCT/type: yes/0
Extra: 01417d46a0b8559577c5c8e01499b52be821c5e1cda41007ae663ca076a1611d800211000000e8e39b962a000000000000000000

1 output(s) for total of 468.496077544000 dcy

stealth address amount amount idx
00: b963710b3a5e41c048cb00d39ad7e485be17ea0cc94e4b5fb835166982129371 468.496077544000 59681 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": 35410, "vin": [ { "gen": { "height": 35400 } } ], "vout": [ { "amount": 468496077544, "target": { "key": "b963710b3a5e41c048cb00d39ad7e485be17ea0cc94e4b5fb835166982129371" } } ], "extra": [ 1, 65, 125, 70, 160, 184, 85, 149, 119, 197, 200, 224, 20, 153, 181, 43, 232, 33, 197, 225, 205, 164, 16, 7, 174, 102, 60, 160, 118, 161, 97, 29, 128, 2, 17, 0, 0, 0, 232, 227, 155, 150, 42, 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