Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2d6f09324b5a3d25366246d1418ba2988cbc44fda29e2757f8a862ec6e55a35

Tx prefix hash: 38ea131e9e8d62f30f24a969f2c916aaa13e2c400148d551eaa349b0c6c2f4ee
Tx public key: fa34343cb06443f1819218664bf3137f21b0f72dae43dce7cd50d2cceec48cd9
Timestamp: 1718683371 Timestamp [UCT]: 2024-06-18 04:02:51 Age [y:d:h:m:s]: 00:294:09:59:47
Block: 1046644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210383 RingCT/type: yes/0
Extra: 01fa34343cb06443f1819218664bf3137f21b0f72dae43dce7cd50d2cceec48cd90211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b72e1ea01f77b8ba6eff2375ea9cd9add160f9a40e2986033828d1b428f66ba4 0.600000000000 1516461 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": 1046654, "vin": [ { "gen": { "height": 1046644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b72e1ea01f77b8ba6eff2375ea9cd9add160f9a40e2986033828d1b428f66ba4" } } ], "extra": [ 1, 250, 52, 52, 60, 176, 100, 67, 241, 129, 146, 24, 102, 75, 243, 19, 127, 33, 176, 247, 45, 174, 67, 220, 231, 205, 80, 210, 204, 238, 196, 140, 217, 2, 17, 0, 0, 0, 3, 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