Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d863b6b4d92ec2f834de3224527fd60a763559531ec80afb02942a57198e38a9

Tx prefix hash: ee890838b78312b145040461e428cbcfb3043aaa3c84e26e496b2421eeaf48b1
Tx public key: c0b32097f67f30ee7ff4d12271c52c6e1b21a6bdc8db505510b166e85ec9aa32
Timestamp: 1713798537 Timestamp [UCT]: 2024-04-22 15:08:57 Age [y:d:h:m:s]: 00:352:17:19:54
Block: 1006142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252153 RingCT/type: yes/0
Extra: 01c0b32097f67f30ee7ff4d12271c52c6e1b21a6bdc8db505510b166e85ec9aa320211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47b3fb912ea55c4396e15456206a82d9d19e5aa71b8ce7c8f3eddda7eb2e68f9 0.600000000000 1467072 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": 1006152, "vin": [ { "gen": { "height": 1006142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47b3fb912ea55c4396e15456206a82d9d19e5aa71b8ce7c8f3eddda7eb2e68f9" } } ], "extra": [ 1, 192, 179, 32, 151, 246, 127, 48, 238, 127, 244, 209, 34, 113, 197, 44, 110, 27, 33, 166, 189, 200, 219, 80, 85, 16, 177, 102, 232, 94, 201, 170, 50, 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