Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f27def69123f8d7c28b7704f7197fcb63d86aa4cec7056f9c895af659e8ffafd

Tx prefix hash: 68906e3fd4f5a86c424877598f519afc70dc5009dac4abcac66ae3248f39c226
Tx public key: ed43263f8040062ba043341c4e03d477b2e4bdb1dcde8b14a0cdd2c132c73962
Timestamp: 1702388229 Timestamp [UCT]: 2023-12-12 13:37:09 Age [y:d:h:m:s]: 01:355:11:40:06
Block: 911564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 512928 RingCT/type: yes/0
Extra: 01ed43263f8040062ba043341c4e03d477b2e4bdb1dcde8b14a0cdd2c132c7396202110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4470adf0e51cbecf42fc72a7fe4e3166363f621b187344cc226632c3d082fe71 0.600000000000 1368776 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": 911574, "vin": [ { "gen": { "height": 911564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4470adf0e51cbecf42fc72a7fe4e3166363f621b187344cc226632c3d082fe71" } } ], "extra": [ 1, 237, 67, 38, 63, 128, 64, 6, 43, 160, 67, 52, 28, 78, 3, 212, 119, 178, 228, 189, 177, 220, 222, 139, 20, 160, 205, 210, 193, 50, 199, 57, 98, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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