Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afd4bcce506c5ee7db01ef23bdc41c76fe3256acd62a9dc73eebad8ccc032928

Tx prefix hash: 154ffbc26559f450b31ae18ec5440587a36ce3a9ac15f234765d6c28e03f889f
Tx public key: efa46812257c523bf240aedf2f91f699e8f3c9c0b37b8b4a219e2abe055583a9
Timestamp: 1742264874 Timestamp [UCT]: 2025-03-18 02:27:54 Age [y:d:h:m:s]: 00:243:14:09:16
Block: 1241676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171819 RingCT/type: yes/0
Extra: 01efa46812257c523bf240aedf2f91f699e8f3c9c0b37b8b4a219e2abe055583a90211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6af424c5f09ccf23f86ead1c05381e303909eaa2c54a668a146fe0ef503d8c56 0.600000000000 1728649 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": 1241686, "vin": [ { "gen": { "height": 1241676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6af424c5f09ccf23f86ead1c05381e303909eaa2c54a668a146fe0ef503d8c56" } } ], "extra": [ 1, 239, 164, 104, 18, 37, 124, 82, 59, 242, 64, 174, 223, 47, 145, 246, 153, 232, 243, 201, 192, 179, 123, 139, 74, 33, 158, 42, 190, 5, 85, 131, 169, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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