Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47ff193569ba002d6015930ee8d92e3497e625d91b0696e35583194db1588ba9

Tx prefix hash: eedef1b9f23798a1cee142961b9e60e3422c4c7e30c0ea5e5ce0677fabe6c552
Tx public key: 802a0b4e75a05f8559fd2e739da8704a758747e779bf3e6cd92dfbd10db0b594
Timestamp: 1722862814 Timestamp [UCT]: 2024-08-05 13:00:14 Age [y:d:h:m:s]: 00:220:23:18:24
Block: 1081287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157835 RingCT/type: yes/0
Extra: 01802a0b4e75a05f8559fd2e739da8704a758747e779bf3e6cd92dfbd10db0b59402110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f0daa2eeb420f63567f506be76159a4fc4e24d5e872c0aec0328b163fda31e3 0.600000000000 1554974 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": 1081297, "vin": [ { "gen": { "height": 1081287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f0daa2eeb420f63567f506be76159a4fc4e24d5e872c0aec0328b163fda31e3" } } ], "extra": [ 1, 128, 42, 11, 78, 117, 160, 95, 133, 89, 253, 46, 115, 157, 168, 112, 74, 117, 135, 71, 231, 121, 191, 62, 108, 217, 45, 251, 209, 13, 176, 181, 148, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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