Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 606b67f8ce96632df5aa79b0515d83b444b6d668e02750c8b807a4742889550b

Tx prefix hash: 07696d9e1b1f7371bde81d528e09d505f509550042e6ea90dd27fb122ee05c52
Tx public key: 3fc8f19beddb4a628b05f3f1e5d27098b5cc162f14ec55f640b5198cdbce71a9
Timestamp: 1714438620 Timestamp [UCT]: 2024-04-30 00:57:00 Age [y:d:h:m:s]: 00:323:10:45:19
Block: 1011444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231233 RingCT/type: yes/0
Extra: 013fc8f19beddb4a628b05f3f1e5d27098b5cc162f14ec55f640b5198cdbce71a90211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93585622151a661a974d76f998362d2366b89add1bfbe011147e97fb5eb8ad12 0.600000000000 1473678 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": 1011454, "vin": [ { "gen": { "height": 1011444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93585622151a661a974d76f998362d2366b89add1bfbe011147e97fb5eb8ad12" } } ], "extra": [ 1, 63, 200, 241, 155, 237, 219, 74, 98, 139, 5, 243, 241, 229, 210, 112, 152, 181, 204, 22, 47, 20, 236, 85, 246, 64, 181, 25, 140, 219, 206, 113, 169, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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