Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b45b5254f08236dcb224bef28c1d5de4e13f10df9a34e5455218bfc9f4349c0

Tx prefix hash: c1d9ce69e248c7306aca70d43306936aea1bc9869536fd9ca5d275e5ff1377ae
Tx public key: 6915176a4338bc1463b44ce946c9362c7bea6cad6b17987e7959e903be48109d
Timestamp: 1717022203 Timestamp [UCT]: 2024-05-29 22:36:43 Age [y:d:h:m:s]: 00:290:14:52:21
Block: 1032866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207724 RingCT/type: yes/0
Extra: 016915176a4338bc1463b44ce946c9362c7bea6cad6b17987e7959e903be48109d0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fc373476cd8b086752b6269cb496cb0dae3ad1980df41c7b7b3cc03721d8c32 0.600000000000 1501321 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": 1032876, "vin": [ { "gen": { "height": 1032866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fc373476cd8b086752b6269cb496cb0dae3ad1980df41c7b7b3cc03721d8c32" } } ], "extra": [ 1, 105, 21, 23, 106, 67, 56, 188, 20, 99, 180, 76, 233, 70, 201, 54, 44, 123, 234, 108, 173, 107, 23, 152, 126, 121, 89, 233, 3, 190, 72, 16, 157, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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