Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5969d2fb5f7918b05c21d58e7e9af702af41d130fa0be906d958563c8c5fe561

Tx prefix hash: 1cd6e1a2516086c0f2b38d0f6c5021e4dfbe8c850a6364c25b88a5dcf52dec6e
Tx public key: cde7734de6b2f70f76049e3dc1b93a3723b8d9bb6a2d37d69bdaaedb18016542
Timestamp: 1579047761 Timestamp [UCT]: 2020-01-15 00:22:41 Age [y:d:h:m:s]: 04:361:21:24:34
Block: 45680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148195 RingCT/type: yes/0
Extra: 01cde7734de6b2f70f76049e3dc1b93a3723b8d9bb6a2d37d69bdaaedb1801654202110000001fbd0f9f9f000000000000000000

1 output(s) for total of 433.178122876000 dcy

stealth address amount amount idx
00: 5fd7016c7bbee12e634435accff5ee37fe152aa1462dcc1983ffc559b8b2e229 433.178122876000 83596 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": 45690, "vin": [ { "gen": { "height": 45680 } } ], "vout": [ { "amount": 433178122876, "target": { "key": "5fd7016c7bbee12e634435accff5ee37fe152aa1462dcc1983ffc559b8b2e229" } } ], "extra": [ 1, 205, 231, 115, 77, 230, 178, 247, 15, 118, 4, 158, 61, 193, 185, 58, 55, 35, 184, 217, 187, 106, 45, 55, 214, 155, 218, 174, 219, 24, 1, 101, 66, 2, 17, 0, 0, 0, 31, 189, 15, 159, 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