Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbbd7ba7c99e6367764890b2a18c02e266ca6f862018d31121caf47d2969e216

Tx prefix hash: a4b8b7e533491cf8afb7e627bcce34f37225fa11a49cec97264ea8348204aead
Tx public key: 4851e0be41408df503b53d2dabdc3027cf6a4d0d70bd8726834d0f6aa43dd27c
Timestamp: 1717838785 Timestamp [UCT]: 2024-06-08 09:26:25 Age [y:d:h:m:s]: 01:008:03:36:18
Block: 1039638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266613 RingCT/type: yes/0
Extra: 014851e0be41408df503b53d2dabdc3027cf6a4d0d70bd8726834d0f6aa43dd27c02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79fd8e66b4b9f347188590632858c1595a4331bbb21a191cee64b79ea8a41fb8 0.600000000000 1508285 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": 1039648, "vin": [ { "gen": { "height": 1039638 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79fd8e66b4b9f347188590632858c1595a4331bbb21a191cee64b79ea8a41fb8" } } ], "extra": [ 1, 72, 81, 224, 190, 65, 64, 141, 245, 3, 181, 61, 45, 171, 220, 48, 39, 207, 106, 77, 13, 112, 189, 135, 38, 131, 77, 15, 106, 164, 61, 210, 124, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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