Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b359a9f5f6eca59e90384a6e06b43f0f34940ef80e0716d54b03f7e1fe6728f2

Tx prefix hash: b6aa78caefdd488ad5f74e71402f40068aefe55f8780d9395f26061f319f06e0
Tx public key: cf64d7b3027d41fec10acbaa6dc153a82f76e07b41dea4adbac8dadd53a041f3
Timestamp: 1738892069 Timestamp [UCT]: 2025-02-07 01:34:29 Age [y:d:h:m:s]: 00:287:10:22:10
Block: 1213753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203180 RingCT/type: yes/0
Extra: 01cf64d7b3027d41fec10acbaa6dc153a82f76e07b41dea4adbac8dadd53a041f30211000000101f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac356b611141b5cc02e6df4aa38d33ed274a862a734930a9008f33b4a91096a4 0.600000000000 1700534 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": 1213763, "vin": [ { "gen": { "height": 1213753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac356b611141b5cc02e6df4aa38d33ed274a862a734930a9008f33b4a91096a4" } } ], "extra": [ 1, 207, 100, 215, 179, 2, 125, 65, 254, 193, 10, 203, 170, 109, 193, 83, 168, 47, 118, 224, 123, 65, 222, 164, 173, 186, 200, 218, 221, 83, 160, 65, 243, 2, 17, 0, 0, 0, 16, 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