Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 564da1fea556fca56fd1dc90df3159ae0970af452566c8dc574eb56590f9ede9

Tx prefix hash: 24406d4d4e1c744afe9dc6ad59daef409fbeab45b2a72b23082a96ba30e28c3a
Tx public key: 5e2896d15400970e2568bdfa3ad439996e86b0d0c9610f513f0ccc22e8b7e8b0
Timestamp: 1736961001 Timestamp [UCT]: 2025-01-15 17:10:01 Age [y:d:h:m:s]: 00:358:06:47:18
Block: 1198005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253668 RingCT/type: yes/0
Extra: 015e2896d15400970e2568bdfa3ad439996e86b0d0c9610f513f0ccc22e8b7e8b0021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cfa71d32ee0b38f7bd8dafe37e584d8faf138a9a0792955bba6002ea0371b3bf 0.600000000000 1684622 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": 1198015, "vin": [ { "gen": { "height": 1198005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfa71d32ee0b38f7bd8dafe37e584d8faf138a9a0792955bba6002ea0371b3bf" } } ], "extra": [ 1, 94, 40, 150, 209, 84, 0, 151, 14, 37, 104, 189, 250, 58, 212, 57, 153, 110, 134, 176, 208, 201, 97, 15, 81, 63, 12, 204, 34, 232, 183, 232, 176, 2, 17, 0, 0, 0, 3, 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