Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 930d78b5087571e82ff6f423cf0638f94904b9e83e326aebfc2de1251c2f6015

Tx prefix hash: 53ad6bd378ca62fc1a130c4a2c4d651a5045df7ff6bb9e55748ed5e790826c39
Tx public key: 5eac173bb719803bea6b355c1a344cc0ba6a8efd765a1f488e6b645a0ccbec06
Timestamp: 1577940135 Timestamp [UCT]: 2020-01-02 04:42:15 Age [y:d:h:m:s]: 04:309:07:56:44
Block: 36922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1110161 RingCT/type: yes/0
Extra: 015eac173bb719803bea6b355c1a344cc0ba6a8efd765a1f488e6b645a0ccbec060211000000104943cd9f000000000000000000

1 output(s) for total of 463.173872831000 dcy

stealth address amount amount idx
00: 2c76fb1a46a336c2fda2aedbdeeb3467b4a6bfa161b10848b7fa314adf542ab9 463.173872831000 62588 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": 36932, "vin": [ { "gen": { "height": 36922 } } ], "vout": [ { "amount": 463173872831, "target": { "key": "2c76fb1a46a336c2fda2aedbdeeb3467b4a6bfa161b10848b7fa314adf542ab9" } } ], "extra": [ 1, 94, 172, 23, 59, 183, 25, 128, 59, 234, 107, 53, 92, 26, 52, 76, 192, 186, 106, 142, 253, 118, 90, 31, 72, 142, 107, 100, 90, 12, 203, 236, 6, 2, 17, 0, 0, 0, 16, 73, 67, 205, 159, 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