Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4268d2f539f5263a963921f0ecfc9ddcdf9b838fac8d5cf8d475e912514ed7a0

Tx prefix hash: 1fbfbb006bb3fabff18e5e0676f766f0de99607f538ffdab5a0a2fb008e92f18
Tx public key: be4ae5b9f6d5bad71e74ae24675a1d5fb32117441958eed6a194fc46b1033c8d
Timestamp: 1704348574 Timestamp [UCT]: 2024-01-04 06:09:34 Age [y:d:h:m:s]: 01:084:22:09:25
Block: 927803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321785 RingCT/type: yes/0
Extra: 01be4ae5b9f6d5bad71e74ae24675a1d5fb32117441958eed6a194fc46b1033c8d021100000003c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 729066b1c4a99b91a2f6f050c747b7f14bf240140b26a1d4a5974102bf707297 0.600000000000 1385639 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": 927813, "vin": [ { "gen": { "height": 927803 } } ], "vout": [ { "amount": 600000000, "target": { "key": "729066b1c4a99b91a2f6f050c747b7f14bf240140b26a1d4a5974102bf707297" } } ], "extra": [ 1, 190, 74, 229, 185, 246, 213, 186, 215, 30, 116, 174, 36, 103, 90, 29, 95, 179, 33, 23, 68, 25, 88, 238, 214, 161, 148, 252, 70, 177, 3, 60, 141, 2, 17, 0, 0, 0, 3, 197, 69, 41, 96, 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