Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d456ff7f2eaa44c002b82258b4ad2ae6b2d46e2ab7f286b3310fcd33bfc457d

Tx prefix hash: 90fc634133e35715929bc11c2b321634da2afd1e838a4b23c935d3b65bf7c07d
Tx public key: 1c9793467988ad3fdccf636495130aeb24a545e01648222a3e47077cedbb0ccb
Timestamp: 1636878998 Timestamp [UCT]: 2021-11-14 08:36:38 Age [y:d:h:m:s]: 03:121:06:40:34
Block: 374091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 865114 RingCT/type: yes/0
Extra: 011c9793467988ad3fdccf636495130aeb24a545e01648222a3e47077cedbb0ccb02110000000142b3953e000000000000000000

1 output(s) for total of 35.357505104000 dcy

stealth address amount amount idx
00: 665dd7fbff2c7a033d42834adb549b6b55e4a7e7c19d58bc34eaf838c24de0c8 35.357505104000 757305 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": 374101, "vin": [ { "gen": { "height": 374091 } } ], "vout": [ { "amount": 35357505104, "target": { "key": "665dd7fbff2c7a033d42834adb549b6b55e4a7e7c19d58bc34eaf838c24de0c8" } } ], "extra": [ 1, 28, 151, 147, 70, 121, 136, 173, 63, 220, 207, 99, 100, 149, 19, 10, 235, 36, 165, 69, 224, 22, 72, 34, 42, 62, 71, 7, 124, 237, 187, 12, 203, 2, 17, 0, 0, 0, 1, 66, 179, 149, 62, 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