Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c2beb0b15e18e29cdb9f17ae121b30d589eabc2355392ca97133b2a708161c1

Tx prefix hash: f1554954a3d6b3b0b0b75de1c9ab6b3910f6998ffcf628f096fe1951ba9d1a10
Tx public key: bb979d6c2bf46a85ffcbd67685bb2f3a1736f967433e96b164af1d838c430eb5
Timestamp: 1718806083 Timestamp [UCT]: 2024-06-19 14:08:03 Age [y:d:h:m:s]: 00:361:12:28:46
Block: 1047661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258292 RingCT/type: yes/0
Extra: 01bb979d6c2bf46a85ffcbd67685bb2f3a1736f967433e96b164af1d838c430eb502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1a6c598ba4b6fdeaa94c4fe4b44832d7ffcd0bcd656c3a0a55b83bc263a841b 0.600000000000 1517540 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": 1047671, "vin": [ { "gen": { "height": 1047661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1a6c598ba4b6fdeaa94c4fe4b44832d7ffcd0bcd656c3a0a55b83bc263a841b" } } ], "extra": [ 1, 187, 151, 157, 108, 43, 244, 106, 133, 255, 203, 214, 118, 133, 187, 47, 58, 23, 54, 249, 103, 67, 62, 150, 177, 100, 175, 29, 131, 140, 67, 14, 181, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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