Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf1b7ff2dfd0e9dd6078b17b90a55a97fe9d4ab01b8b0170af1a54936244085d

Tx prefix hash: 700641f03c8d4e9b8daad2218ceb254e0bb1d560c8b25f6add1a601a4a3b8ea8
Tx public key: 8c14db501cfd5c9f933182e3ad1a63db55d270a2f5967b64b1845e3a60462916
Timestamp: 1698385535 Timestamp [UCT]: 2023-10-27 05:45:35 Age [y:d:h:m:s]: 01:156:17:09:56
Block: 878579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372992 RingCT/type: yes/0
Extra: 018c14db501cfd5c9f933182e3ad1a63db55d270a2f5967b64b1845e3a60462916021100000012e6d27f9c000000000000000000

1 output(s) for total of 0.753267445000 dcy

stealth address amount amount idx
00: 90aa3a0992f10d0ce939754b61263a6f62abbd39465166da9945257dcae113fb 0.753267445000 1334031 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": 878589, "vin": [ { "gen": { "height": 878579 } } ], "vout": [ { "amount": 753267445, "target": { "key": "90aa3a0992f10d0ce939754b61263a6f62abbd39465166da9945257dcae113fb" } } ], "extra": [ 1, 140, 20, 219, 80, 28, 253, 92, 159, 147, 49, 130, 227, 173, 26, 99, 219, 85, 210, 112, 162, 245, 150, 123, 100, 177, 132, 94, 58, 96, 70, 41, 22, 2, 17, 0, 0, 0, 18, 230, 210, 127, 156, 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