Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21095938f49a189a2f04affe0e58fc67559bf7d4e6461312badf794b5783d5a6

Tx prefix hash: aead20901aee9de82aea280e068c4b66cf02895eaebc97a94f17359194faf93c
Tx public key: f6dbd64f0e4a3e282d059dd2e849b185e3e2d272963f82672ff39a998c29c734
Timestamp: 1722778285 Timestamp [UCT]: 2024-08-04 13:31:25 Age [y:d:h:m:s]: 00:159:02:36:42
Block: 1080580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113831 RingCT/type: yes/0
Extra: 01f6dbd64f0e4a3e282d059dd2e849b185e3e2d272963f82672ff39a998c29c73402110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33777a9c934faf4405c50f5ec6731b04e936a0b14ce5f17ff9c1d5aaaadd845a 0.600000000000 1554003 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": 1080590, "vin": [ { "gen": { "height": 1080580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33777a9c934faf4405c50f5ec6731b04e936a0b14ce5f17ff9c1d5aaaadd845a" } } ], "extra": [ 1, 246, 219, 214, 79, 14, 74, 62, 40, 45, 5, 157, 210, 232, 73, 177, 133, 227, 226, 210, 114, 150, 63, 130, 103, 47, 243, 154, 153, 140, 41, 199, 52, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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