Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6f96b1c0c71f564b13e5bbde48b2910531b863785d72f30c293e2b3f1c7491e

Tx prefix hash: 62e3a854dbd0d6456cc1ebfa2ea8c735df1ea7d3133cacd1fcf9c98b92b649ef
Tx public key: 1de78731f3dd0f4a10690b50de6b823a6ce94d2d79e248e4a74c399aa44707fc
Timestamp: 1713015075 Timestamp [UCT]: 2024-04-13 13:31:15 Age [y:d:h:m:s]: 00:356:16:14:23
Block: 999631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255006 RingCT/type: yes/0
Extra: 011de78731f3dd0f4a10690b50de6b823a6ce94d2d79e248e4a74c399aa44707fc02110000001b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85dfb1b17e719a2316e70e9f48feb9e24b186072ee327b9e6e273baf96b0daa3 0.600000000000 1460113 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": 999641, "vin": [ { "gen": { "height": 999631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85dfb1b17e719a2316e70e9f48feb9e24b186072ee327b9e6e273baf96b0daa3" } } ], "extra": [ 1, 29, 231, 135, 49, 243, 221, 15, 74, 16, 105, 11, 80, 222, 107, 130, 58, 108, 233, 77, 45, 121, 226, 72, 228, 167, 76, 57, 154, 164, 71, 7, 252, 2, 17, 0, 0, 0, 27, 89, 218, 211, 245, 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