Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14bbb9987db235e536e12a2977c8cab7912e83cf17fea58ffa02f89f23edf760

Tx prefix hash: 8428e7ca897a7b5097ebf7e418525969c61aaa5ac89201d8c38d04bf316e1c5c
Tx public key: 7e60877bccb111d3ec21a470a679aafa4199ae17171f0a6fd6c45301324d95ba
Timestamp: 1636255684 Timestamp [UCT]: 2021-11-07 03:28:04 Age [y:d:h:m:s]: 03:169:12:33:19
Block: 368998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 899540 RingCT/type: yes/0
Extra: 017e60877bccb111d3ec21a470a679aafa4199ae17171f0a6fd6c45301324d95ba0211000000174f792ffd000000000000000000

1 output(s) for total of 36.758420653000 dcy

stealth address amount amount idx
00: 5d6322c074cefd122fe7c2769d3c6b9f907d1a430f675e60d1a4c8639386e40e 36.758420653000 748306 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": 369008, "vin": [ { "gen": { "height": 368998 } } ], "vout": [ { "amount": 36758420653, "target": { "key": "5d6322c074cefd122fe7c2769d3c6b9f907d1a430f675e60d1a4c8639386e40e" } } ], "extra": [ 1, 126, 96, 135, 123, 204, 177, 17, 211, 236, 33, 164, 112, 166, 121, 170, 250, 65, 153, 174, 23, 23, 31, 10, 111, 214, 196, 83, 1, 50, 77, 149, 186, 2, 17, 0, 0, 0, 23, 79, 121, 47, 253, 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