Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c7968e9daf4fd32f93743df65b641bda1002e2e4d8c73f5e897e490167e35a1

Tx prefix hash: 78a82b302b6730f0de700ca5ec7dcc92b3ad3341d6ef07c0f5c6404b6c70042a
Tx public key: 86b583b662cfeb6faf932c70147d2169ae8be9323e3d8f7975b55d8b010d53af
Timestamp: 1639264855 Timestamp [UCT]: 2021-12-11 23:20:55 Age [y:d:h:m:s]: 03:057:01:36:01
Block: 393492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 819517 RingCT/type: yes/0
Extra: 0186b583b662cfeb6faf932c70147d2169ae8be9323e3d8f7975b55d8b010d53af0211000000060eb261b4000000000000000000

1 output(s) for total of 30.492850089000 dcy

stealth address amount amount idx
00: 7df4fbc1986857dc285d96933c73a0de0a67ae1a83a18eb28f4f9c08f0d14577 30.492850089000 790749 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": 393502, "vin": [ { "gen": { "height": 393492 } } ], "vout": [ { "amount": 30492850089, "target": { "key": "7df4fbc1986857dc285d96933c73a0de0a67ae1a83a18eb28f4f9c08f0d14577" } } ], "extra": [ 1, 134, 181, 131, 182, 98, 207, 235, 111, 175, 147, 44, 112, 20, 125, 33, 105, 174, 139, 233, 50, 62, 61, 143, 121, 117, 181, 93, 139, 1, 13, 83, 175, 2, 17, 0, 0, 0, 6, 14, 178, 97, 180, 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