Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40dd146333e8dc43be64790685eb4aae2f8249b71d2effb80baad17231a09efa

Tx prefix hash: 0b4fe9031bc787fd532c17609dddf07992a18e75aa8c9ebcfa48fdea3112e7d2
Tx public key: 7300b378e7e862d9e517622f5a87d7faf817dc943f5789b9014912b46adc25af
Timestamp: 1578154983 Timestamp [UCT]: 2020-01-04 16:23:03 Age [y:d:h:m:s]: 04:306:18:04:23
Block: 38648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1108382 RingCT/type: yes/0
Extra: 017300b378e7e862d9e517622f5a87d7faf817dc943f5789b9014912b46adc25af0211000000104ac5aa02000000000000000000

1 output(s) for total of 457.029235413000 dcy

stealth address amount amount idx
00: bbf43f417e495be34c32515a76eef3314626edb006a6818a4c004a95c96d52a9 457.029235413000 66040 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": 38658, "vin": [ { "gen": { "height": 38648 } } ], "vout": [ { "amount": 457029235413, "target": { "key": "bbf43f417e495be34c32515a76eef3314626edb006a6818a4c004a95c96d52a9" } } ], "extra": [ 1, 115, 0, 179, 120, 231, 232, 98, 217, 229, 23, 98, 47, 90, 135, 215, 250, 248, 23, 220, 148, 63, 87, 137, 185, 1, 73, 18, 180, 106, 220, 37, 175, 2, 17, 0, 0, 0, 16, 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