Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af4b9ea552126019e802cd9a2a64506fac63eddc29c8a6a8f1031dc387fa7f28

Tx prefix hash: 40eb2a934ddae7a812c96ebef8eed65225a82a1e5cefd338d2c799d85cae3488
Tx public key: 874122bc9a5f3aeb9dcf28e3c8a47756e51cf89a8a294e4ae79715804f780bd2
Timestamp: 1745911521 Timestamp [UCT]: 2025-04-29 07:25:21 Age [y:d:h:m:s]: 00:271:04:34:20
Block: 1271866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191430 RingCT/type: yes/0
Extra: 01874122bc9a5f3aeb9dcf28e3c8a47756e51cf89a8a294e4ae79715804f780bd202110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb767b9084f12aa2d593213f9ec4bb346e40ad1857e3cc33f679f997b142a833 0.600000000000 1759135 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": 1271876, "vin": [ { "gen": { "height": 1271866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb767b9084f12aa2d593213f9ec4bb346e40ad1857e3cc33f679f997b142a833" } } ], "extra": [ 1, 135, 65, 34, 188, 154, 95, 58, 235, 157, 207, 40, 227, 200, 164, 119, 86, 229, 28, 248, 154, 138, 41, 78, 74, 231, 151, 21, 128, 79, 120, 11, 210, 2, 17, 0, 0, 0, 3, 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