Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 829f1a1e1a824e52d097d568e00f954a3a1810f08990b4a59f10f46a86c0461f

Tx prefix hash: 4426d2bc0b80c55109adc867588bd04dfef35474eb2495df1f65096ca5562e86
Tx public key: bc4e8493922da380651c40d197c28e7946a55d34c758264bd8be30b3f6a2d733
Timestamp: 1736038113 Timestamp [UCT]: 2025-01-05 00:48:33 Age [y:d:h:m:s]: 00:313:04:56:59
Block: 1190395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221350 RingCT/type: yes/0
Extra: 01bc4e8493922da380651c40d197c28e7946a55d34c758264bd8be30b3f6a2d73302110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12fad5b46e5c283381bf0d4560dcd1f21c58392734e3e3c3f877749cd75e7bf1 0.600000000000 1676910 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": 1190405, "vin": [ { "gen": { "height": 1190395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12fad5b46e5c283381bf0d4560dcd1f21c58392734e3e3c3f877749cd75e7bf1" } } ], "extra": [ 1, 188, 78, 132, 147, 146, 45, 163, 128, 101, 28, 64, 209, 151, 194, 142, 121, 70, 165, 93, 52, 199, 88, 38, 75, 216, 190, 48, 179, 246, 162, 215, 51, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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