Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 136d7c506813488d86406840262a6a08d7ff6c3aaec5177fb817005993510e4e

Tx prefix hash: fd474673a2eff6e66eebbba426ef326f57238542ce6307311625c2d5a1c5629c
Tx public key: d71b8cb89687b47337196d20923a5f40f51b9039f869b10e39e6fd71e8110e7c
Timestamp: 1702934915 Timestamp [UCT]: 2023-12-18 21:28:35 Age [y:d:h:m:s]: 01:155:04:50:37
Block: 916076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372099 RingCT/type: yes/0
Extra: 01d71b8cb89687b47337196d20923a5f40f51b9039f869b10e39e6fd71e8110e7c02110000000d75e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 851684cf1be09a6d3ecbeeafa8c6999db1307e190c3868a4644890f8642f40dc 0.600000000000 1373550 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": 916086, "vin": [ { "gen": { "height": 916076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "851684cf1be09a6d3ecbeeafa8c6999db1307e190c3868a4644890f8642f40dc" } } ], "extra": [ 1, 215, 27, 140, 184, 150, 135, 180, 115, 55, 25, 109, 32, 146, 58, 95, 64, 245, 27, 144, 57, 248, 105, 177, 14, 57, 230, 253, 113, 232, 17, 14, 124, 2, 17, 0, 0, 0, 13, 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