Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cd8066ac6cb94a7b197acde38edbaacdecd14bf6961cacd84b0748d91333809

Tx prefix hash: 6ea33c17cb30b00e501dc2f78ef9a25ce6424ecb6f53deb9c9191c2c520ba52b
Tx public key: f29e0a95ff7a6520f8e54254aa03dc1b8028b0860ff1f24bbfdef1242075b621
Timestamp: 1735146077 Timestamp [UCT]: 2024-12-25 17:01:17 Age [y:d:h:m:s]: 00:096:05:15:30
Block: 1183007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68546 RingCT/type: yes/0
Extra: 01f29e0a95ff7a6520f8e54254aa03dc1b8028b0860ff1f24bbfdef1242075b621021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c40fa7be3b59e6361f9d929133dadb0af49c5316455cd59c924cc752382a231d 0.600000000000 1669446 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": 1183017, "vin": [ { "gen": { "height": 1183007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c40fa7be3b59e6361f9d929133dadb0af49c5316455cd59c924cc752382a231d" } } ], "extra": [ 1, 242, 158, 10, 149, 255, 122, 101, 32, 248, 229, 66, 84, 170, 3, 220, 27, 128, 40, 176, 134, 15, 241, 242, 75, 191, 222, 241, 36, 32, 117, 182, 33, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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