Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5b13f09c02c5c41a0ac68f3b1dc5dd91d1a25184bb96266ff2016453f3f54e3

Tx prefix hash: 8e3491225ed846c167ab7f6d1188595a9fcd5aa70f930e6d94e2be8089eb7caf
Tx public key: 1b0639c779da517e772e2b6e9690a1fd55c0d99b337ec23ab5d4d941c384f8f8
Timestamp: 1727553596 Timestamp [UCT]: 2024-09-28 19:59:56 Age [y:d:h:m:s]: 00:218:10:14:29
Block: 1120181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155928 RingCT/type: yes/0
Extra: 011b0639c779da517e772e2b6e9690a1fd55c0d99b337ec23ab5d4d941c384f8f8021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fdf36d3cb3e4f25c55a2cae843c9f83dd2c68ee3c93d7c98de82898a0c6a084 0.600000000000 1602006 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": 1120191, "vin": [ { "gen": { "height": 1120181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fdf36d3cb3e4f25c55a2cae843c9f83dd2c68ee3c93d7c98de82898a0c6a084" } } ], "extra": [ 1, 27, 6, 57, 199, 121, 218, 81, 126, 119, 46, 43, 110, 150, 144, 161, 253, 85, 192, 217, 155, 51, 126, 194, 58, 181, 212, 217, 65, 195, 132, 248, 248, 2, 17, 0, 0, 0, 4, 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