Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18f7480184a4031b0412a7952e7f010e4b6d6dedd16f18754a08e877ab2504ff

Tx prefix hash: e5276f8523f959f20f74cb95689cb1d35bb61677240aa2e15cb888a99dffc9d6
Tx public key: 7cfe1d691d3104a79e736ad4837f39a7c6d45e3090cb84b798224368d7e64bc4
Timestamp: 1730853155 Timestamp [UCT]: 2024-11-06 00:32:35 Age [y:d:h:m:s]: 00:191:00:30:26
Block: 1147440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136380 RingCT/type: yes/0
Extra: 017cfe1d691d3104a79e736ad4837f39a7c6d45e3090cb84b798224368d7e64bc4021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 338dcadb0fd8648f42cc9f956afc91667a531cb955227736905a2fbe391d84fe 0.600000000000 1632135 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": 1147450, "vin": [ { "gen": { "height": 1147440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "338dcadb0fd8648f42cc9f956afc91667a531cb955227736905a2fbe391d84fe" } } ], "extra": [ 1, 124, 254, 29, 105, 29, 49, 4, 167, 158, 115, 106, 212, 131, 127, 57, 167, 198, 212, 94, 48, 144, 203, 132, 183, 152, 34, 67, 104, 215, 230, 75, 196, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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