Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 855a9816cc376508900ffa8119c91d1d6787b7100d42eef28cf445b230c74d0a

Tx prefix hash: d79ba65fa865c38510c84c75a4750707057933bba050a255a4e3a951c3f4e4fb
Tx public key: ec7166996ef4ac38e800feafd8432b04a1d718b6c5e7e7ecc9651cde8693ae9b
Timestamp: 1738331130 Timestamp [UCT]: 2025-01-31 13:45:30 Age [y:d:h:m:s]: 00:293:14:41:25
Block: 1209107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207593 RingCT/type: yes/0
Extra: 01ec7166996ef4ac38e800feafd8432b04a1d718b6c5e7e7ecc9651cde8693ae9b021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5fe6cd61d7bd9ae46e1f2e25036b71d692baeee51aac8de48bb9e395a8e0f2b 0.600000000000 1695848 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": 1209117, "vin": [ { "gen": { "height": 1209107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5fe6cd61d7bd9ae46e1f2e25036b71d692baeee51aac8de48bb9e395a8e0f2b" } } ], "extra": [ 1, 236, 113, 102, 153, 110, 244, 172, 56, 232, 0, 254, 175, 216, 67, 43, 4, 161, 215, 24, 182, 197, 231, 231, 236, 201, 101, 28, 222, 134, 147, 174, 155, 2, 17, 0, 0, 0, 6, 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