Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6295bb208378867bd2c3cc704ddf263611aff47e901f7c2dc8d30d12ab2b7d7

Tx prefix hash: b49ec0fd198f1af04652abfe1820308fe5e3d1d60aacdabab69385e7645069e7
Tx public key: 5b49150455bc0bd7ed5d9a6ea81a3ddbeb381777cd56ac4737280080b68b2f2a
Timestamp: 1681446690 Timestamp [UCT]: 2023-04-14 04:31:30 Age [y:d:h:m:s]: 01:273:03:14:21
Block: 738167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456718 RingCT/type: yes/0
Extra: 015b49150455bc0bd7ed5d9a6ea81a3ddbeb381777cd56ac4737280080b68b2f2a021100000004b3164c24000000000000000000

1 output(s) for total of 2.198601509000 dcy

stealth address amount amount idx
00: 043df6ccfb48b3b276a58ce81598d9e7818cb290dc97d626f6cb6bebda155a0b 2.198601509000 1184820 of 0

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": 738177, "vin": [ { "gen": { "height": 738167 } } ], "vout": [ { "amount": 2198601509, "target": { "key": "043df6ccfb48b3b276a58ce81598d9e7818cb290dc97d626f6cb6bebda155a0b" } } ], "extra": [ 1, 91, 73, 21, 4, 85, 188, 11, 215, 237, 93, 154, 110, 168, 26, 61, 219, 235, 56, 23, 119, 205, 86, 172, 71, 55, 40, 0, 128, 182, 139, 47, 42, 2, 17, 0, 0, 0, 4, 179, 22, 76, 36, 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