Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d8f414e8d05efb516c8d797f077f21638c8f50453b20e5b22d895551ddbce56

Tx prefix hash: 337ff4f3010510ae2b88807085551c3d589cbd1a56e8fd42968a69d816e67013
Tx public key: cc256c410357e84201b2a0f21c89f900ae168d151aec4339ba75b8228bb0aa4e
Timestamp: 1704963160 Timestamp [UCT]: 2024-01-11 08:52:40 Age [y:d:h:m:s]: 01:068:01:41:56
Block: 932880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309764 RingCT/type: yes/0
Extra: 01cc256c410357e84201b2a0f21c89f900ae168d151aec4339ba75b8228bb0aa4e02110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd80fe7cbc40fe1b8028ae3f9d86c052966663c3bda8955595cc3b0760ac53cb 0.600000000000 1390820 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": 932890, "vin": [ { "gen": { "height": 932880 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd80fe7cbc40fe1b8028ae3f9d86c052966663c3bda8955595cc3b0760ac53cb" } } ], "extra": [ 1, 204, 37, 108, 65, 3, 87, 232, 66, 1, 178, 160, 242, 28, 137, 249, 0, 174, 22, 141, 21, 26, 236, 67, 57, 186, 117, 184, 34, 139, 176, 170, 78, 2, 17, 0, 0, 0, 9, 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