Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3577e989882e173f393dda826ba637bbcc6c913b3936488774a0b59bf679b947

Tx prefix hash: 8816c88bc77a6b8fa0f2a1f1d935b9c7d7787f6b4a75e920abf9db070f0df3fe
Tx public key: 388852a831bf4a4d02f3b62f3847c113fbdac326e19153b85f0f252211724f9d
Timestamp: 1730450147 Timestamp [UCT]: 2024-11-01 08:35:47 Age [y:d:h:m:s]: 00:138:13:54:34
Block: 1144106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98897 RingCT/type: yes/0
Extra: 01388852a831bf4a4d02f3b62f3847c113fbdac326e19153b85f0f252211724f9d0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96579c2af82779a202184ac0d721b440c4b9083562ab7678c6b19471e4b5479a 0.600000000000 1628205 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": 1144116, "vin": [ { "gen": { "height": 1144106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96579c2af82779a202184ac0d721b440c4b9083562ab7678c6b19471e4b5479a" } } ], "extra": [ 1, 56, 136, 82, 168, 49, 191, 74, 77, 2, 243, 182, 47, 56, 71, 193, 19, 251, 218, 195, 38, 225, 145, 83, 184, 95, 15, 37, 34, 17, 114, 79, 157, 2, 17, 0, 0, 0, 1, 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