Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cc980b6de700ab9736d938437be8dd3cba572b513f85d801289f593b7e11289

Tx prefix hash: dc13fb79737e46264f099ea1955fd4c739e441e9af254c79f07cd59c73d4bb2b
Tx public key: 0ec0863faf8136b95b8f729d24e1a649e788dcb4b696a1b6f264a77413fba295
Timestamp: 1713576735 Timestamp [UCT]: 2024-04-20 01:32:15 Age [y:d:h:m:s]: 01:033:02:57:54
Block: 1004281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284665 RingCT/type: yes/0
Extra: 010ec0863faf8136b95b8f729d24e1a649e788dcb4b696a1b6f264a77413fba2950211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f7801f5c977ae444f4319e9e82bd9fa4bc9df929ed31be63bfbf724c0ab7749 0.600000000000 1464849 of 15

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": 1004291, "vin": [ { "gen": { "height": 1004281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f7801f5c977ae444f4319e9e82bd9fa4bc9df929ed31be63bfbf724c0ab7749" } } ], "extra": [ 1, 14, 192, 134, 63, 175, 129, 54, 185, 91, 143, 114, 157, 36, 225, 166, 73, 231, 136, 220, 180, 182, 150, 161, 182, 242, 100, 167, 116, 19, 251, 162, 149, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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