Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5eced4183a9d6bd5e0b0c204d270530070aacedefae4522cc482802eab75698

Tx prefix hash: fb07bb5583900e1df2b5aef134efe6d8180ff2f3dda74d6a1952a1f7c605bba4
Tx public key: a39a33c47a39e31ad693f4c7fc7de786f8e1eb1f145c513ca601d02b65853835
Timestamp: 1740565359 Timestamp [UCT]: 2025-02-26 10:22:39 Age [y:d:h:m:s]: 00:338:18:30:11
Block: 1227584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239795 RingCT/type: yes/0
Extra: 01a39a33c47a39e31ad693f4c7fc7de786f8e1eb1f145c513ca601d02b65853835021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4cc0eb03802dadbc46dc3f3d2d28a8a51b2498e0e68e0c3c10d1559486e0027 0.600000000000 1714459 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": 1227594, "vin": [ { "gen": { "height": 1227584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4cc0eb03802dadbc46dc3f3d2d28a8a51b2498e0e68e0c3c10d1559486e0027" } } ], "extra": [ 1, 163, 154, 51, 196, 122, 57, 227, 26, 214, 147, 244, 199, 252, 125, 231, 134, 248, 225, 235, 31, 20, 92, 81, 60, 166, 1, 208, 43, 101, 133, 56, 53, 2, 17, 0, 0, 0, 4, 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