Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 752c16a5aa03188874b0475f07c3edc44b4bccb308fe8de52055d097702840b9

Tx prefix hash: 1392d74671014a800553f9740d928fd3c5ce7f5cc6262541ce12f0f0312001e5
Tx public key: 603163e58d1edd120e748df41c98795756d4c70d1e87df0b24d89aa6fd384f14
Timestamp: 1737047168 Timestamp [UCT]: 2025-01-16 17:06:08 Age [y:d:h:m:s]: 00:338:13:40:43
Block: 1198738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239531 RingCT/type: yes/0
Extra: 01603163e58d1edd120e748df41c98795756d4c70d1e87df0b24d89aa6fd384f14021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcc6020934feb0e5f691544b32cde1275078520e1cec9bb9af44fd11a8227d33 0.600000000000 1685365 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": 1198748, "vin": [ { "gen": { "height": 1198738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcc6020934feb0e5f691544b32cde1275078520e1cec9bb9af44fd11a8227d33" } } ], "extra": [ 1, 96, 49, 99, 229, 141, 30, 221, 18, 14, 116, 141, 244, 28, 152, 121, 87, 86, 212, 199, 13, 30, 135, 223, 11, 36, 216, 154, 166, 253, 56, 79, 20, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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