Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 759f637dab37666bda47addcc635d796a0c9d321c544fb45d2b85ac802c1285f

Tx prefix hash: 002fd4e4209a7b7ec66cbb6a8d7719c27aae9fc45ea86deda49d3c4417b0f1b9
Tx public key: 4f15d8275280b4c5b0e87d0c94ebd401d5474243c3af831e8390aa3756bd1811
Timestamp: 1672872376 Timestamp [UCT]: 2023-01-04 22:46:16 Age [y:d:h:m:s]: 01:332:19:51:02
Block: 667708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498889 RingCT/type: yes/0
Extra: 014f15d8275280b4c5b0e87d0c94ebd401d5474243c3af831e8390aa3756bd181102110000000152542ceb000000000000000000

1 output(s) for total of 3.763623554000 dcy

stealth address amount amount idx
00: 1cf7e76942288e5c613ca22f367266aab01c7bf912c33aee9e59e2eb1ce45fb9 3.763623554000 1108923 of 0

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": 667718, "vin": [ { "gen": { "height": 667708 } } ], "vout": [ { "amount": 3763623554, "target": { "key": "1cf7e76942288e5c613ca22f367266aab01c7bf912c33aee9e59e2eb1ce45fb9" } } ], "extra": [ 1, 79, 21, 216, 39, 82, 128, 180, 197, 176, 232, 125, 12, 148, 235, 212, 1, 213, 71, 66, 67, 195, 175, 131, 30, 131, 144, 170, 55, 86, 189, 24, 17, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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