Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18c170ac519ad582e8d6c47bb49cbc868a1f095da60d2ad608dd6a8a2e4799bf

Tx prefix hash: 41cd3e743d2f61b609c7529a0deab0808f6befeacccebeb4eb1d1765e4c720dd
Tx public key: 1c95afa4123a2d477667b92479eb435c5c2069c1ccc3cb9b30c535c98d311c87
Timestamp: 1726762499 Timestamp [UCT]: 2024-09-19 16:14:59 Age [y:d:h:m:s]: 00:034:05:08:34
Block: 1113621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24478 RingCT/type: yes/0
Extra: 011c95afa4123a2d477667b92479eb435c5c2069c1ccc3cb9b30c535c98d311c8702110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9eb75dff313f79316aa7eb54d61b8025412aefdea5a3cf10b52f48876ea2102d 0.600000000000 1593360 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": 1113631, "vin": [ { "gen": { "height": 1113621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9eb75dff313f79316aa7eb54d61b8025412aefdea5a3cf10b52f48876ea2102d" } } ], "extra": [ 1, 28, 149, 175, 164, 18, 58, 45, 71, 118, 103, 185, 36, 121, 235, 67, 92, 92, 32, 105, 193, 204, 195, 203, 155, 48, 197, 53, 201, 141, 49, 28, 135, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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