Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb836693100edfff31c1dac0419a9e66d7c4f8d7319437d80bbe1cc5aa1f04e2

Tx prefix hash: 220c39361846e148b3c8f5d764a5374cd329d13a86b8c5f55ead966bf7833d1d
Tx public key: f780e1f7472ae445cc1c7d0209279667a2c248ed1555ca39c9a8c9f743678f3e
Timestamp: 1639824931 Timestamp [UCT]: 2021-12-18 10:55:31 Age [y:d:h:m:s]: 02:328:07:24:57
Block: 398136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 752709 RingCT/type: yes/0
Extra: 01f780e1f7472ae445cc1c7d0209279667a2c248ed1555ca39c9a8c9f743678f3e0211000000017659c797000000000000000000

1 output(s) for total of 29.431372271000 dcy

stealth address amount amount idx
00: 35e5eb8c24eaeef9e3b8c9341f50186a0e4b03732adef07e4cf6c40db8a69273 29.431372271000 796910 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": 398146, "vin": [ { "gen": { "height": 398136 } } ], "vout": [ { "amount": 29431372271, "target": { "key": "35e5eb8c24eaeef9e3b8c9341f50186a0e4b03732adef07e4cf6c40db8a69273" } } ], "extra": [ 1, 247, 128, 225, 247, 71, 42, 228, 69, 204, 28, 125, 2, 9, 39, 150, 103, 162, 194, 72, 237, 21, 85, 202, 57, 201, 168, 201, 247, 67, 103, 143, 62, 2, 17, 0, 0, 0, 1, 118, 89, 199, 151, 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