Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf46b860e54a83c6e82a68bb4746ce94c39805165ed6802c75868ac21d932d9a

Tx prefix hash: 114d9ac6f5a67b455602901dc6e49ef4213d02be169d11a98a62a09ad0e0d6e3
Tx public key: 00c8a5735f44ad8aa79b3086171d1ff3bdaa7d5eab14c2f64e62a067d4785a9e
Timestamp: 1634875096 Timestamp [UCT]: 2021-10-22 03:58:16 Age [y:d:h:m:s]: 03:128:03:53:32
Block: 357848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 869663 RingCT/type: yes/0
Extra: 0100c8a5735f44ad8aa79b3086171d1ff3bdaa7d5eab14c2f64e62a067d4785a9e02110000000106faf294000000000000000000

1 output(s) for total of 40.022244273000 dcy

stealth address amount amount idx
00: ddde2ad04a28bde7d1aae150d7a839b3f221aee7f8df5cc53ee0ca0661e00de2 40.022244273000 729476 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": 357858, "vin": [ { "gen": { "height": 357848 } } ], "vout": [ { "amount": 40022244273, "target": { "key": "ddde2ad04a28bde7d1aae150d7a839b3f221aee7f8df5cc53ee0ca0661e00de2" } } ], "extra": [ 1, 0, 200, 165, 115, 95, 68, 173, 138, 167, 155, 48, 134, 23, 29, 31, 243, 189, 170, 125, 94, 171, 20, 194, 246, 78, 98, 160, 103, 212, 120, 90, 158, 2, 17, 0, 0, 0, 1, 6, 250, 242, 148, 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