Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cff2159891aab38462848bb7a0fda20e56f9d1892dadf68c75e2d137137488d7

Tx prefix hash: cd1caefe0a97214e16dc9c03f438ffbcaa4fb6398a05151e8f1b75451f406b58
Tx public key: d359b0dc77af8eb6238537b8124d231aa638658b74720ebf6b1f138e4ce8a02f
Timestamp: 1581364997 Timestamp [UCT]: 2020-02-10 20:03:17 Age [y:d:h:m:s]: 04:323:12:10:17
Block: 62257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123336 RingCT/type: yes/0
Extra: 01d359b0dc77af8eb6238537b8124d231aa638658b74720ebf6b1f138e4ce8a02f02110162263500000000000000000000000000

1 output(s) for total of 381.695930699000 dcy

stealth address amount amount idx
00: 17922abb0aaa17f33aeade4e17a7f600dbe6d77111e50a599a962d296ae6f260 381.695930699000 114816 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": 62267, "vin": [ { "gen": { "height": 62257 } } ], "vout": [ { "amount": 381695930699, "target": { "key": "17922abb0aaa17f33aeade4e17a7f600dbe6d77111e50a599a962d296ae6f260" } } ], "extra": [ 1, 211, 89, 176, 220, 119, 175, 142, 182, 35, 133, 55, 184, 18, 77, 35, 26, 166, 56, 101, 139, 116, 114, 14, 191, 107, 31, 19, 142, 76, 232, 160, 47, 2, 17, 1, 98, 38, 53, 0, 0, 0, 0, 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