Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5494837198f73ff6c6ebc10d2298e1e22ed704ca5b4c01cc34e4cadaa0225f72

Tx prefix hash: 4ef1b4c02b4e529464f3c5c241033754136c17ea5a1919bef43d1e501f4cae32
Tx public key: 14464d19f277143e5f3839fda1357a75b34194d59955f8cc7386b02213a06db9
Timestamp: 1706506024 Timestamp [UCT]: 2024-01-29 05:27:04 Age [y:d:h:m:s]: 01:071:22:06:59
Block: 945662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312490 RingCT/type: yes/0
Extra: 0114464d19f277143e5f3839fda1357a75b34194d59955f8cc7386b02213a06db902110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e81e4fb098c4a3b0fb8783b04a7bc19c800ee9fee914d8be864afc164c629df 0.600000000000 1403978 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": 945672, "vin": [ { "gen": { "height": 945662 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e81e4fb098c4a3b0fb8783b04a7bc19c800ee9fee914d8be864afc164c629df" } } ], "extra": [ 1, 20, 70, 77, 25, 242, 119, 20, 62, 95, 56, 57, 253, 161, 53, 122, 117, 179, 65, 148, 213, 153, 85, 248, 204, 115, 134, 176, 34, 19, 160, 109, 185, 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