Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ad31e85f58e158805ec9e9ddd456ed1604b63d0e3b21353703b17eff102a774

Tx prefix hash: f8c873f7b36dd2d8a5e2d56abf8a753e7b9f2c911f65bfe2768e39c1811755b4
Tx public key: b6f80eff6b3ad56986191254b24849975560628a4d8d660fd5f4b98d8440a33c
Timestamp: 1702250335 Timestamp [UCT]: 2023-12-10 23:18:55 Age [y:d:h:m:s]: 01:037:03:02:13
Block: 910399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287893 RingCT/type: yes/0
Extra: 01b6f80eff6b3ad56986191254b24849975560628a4d8d660fd5f4b98d8440a33c02110000000333af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b676ee6411349b0ec34b270c4b0f88e7f1ca5d27d00c4395fd11c8f745ec5258 0.600000000000 1367554 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": 910409, "vin": [ { "gen": { "height": 910399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b676ee6411349b0ec34b270c4b0f88e7f1ca5d27d00c4395fd11c8f745ec5258" } } ], "extra": [ 1, 182, 248, 14, 255, 107, 58, 213, 105, 134, 25, 18, 84, 178, 72, 73, 151, 85, 96, 98, 138, 77, 141, 102, 15, 213, 244, 185, 141, 132, 64, 163, 60, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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