Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 363169ac643e30bfc77e5e60a749745a469bc0de4c3cedd0f529f1db6c021ce9

Tx prefix hash: ce5174125b694da3dbc59aa8ede3a1d7183d66299857ef2381ecd8216929b2ee
Tx public key: aae2867f1837c1cb3af00c9330f4a129e68d6e2a814bd81aa37716e3083d9215
Timestamp: 1702027693 Timestamp [UCT]: 2023-12-08 09:28:13 Age [y:d:h:m:s]: 01:160:13:54:55
Block: 908552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375932 RingCT/type: yes/0
Extra: 01aae2867f1837c1cb3af00c9330f4a129e68d6e2a814bd81aa37716e3083d9215021100000004faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5aad925cec1c818195155f7cf2c0771a82cc5182ae00f9bb107ee73197a18ba2 0.600000000000 1365589 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": 908562, "vin": [ { "gen": { "height": 908552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5aad925cec1c818195155f7cf2c0771a82cc5182ae00f9bb107ee73197a18ba2" } } ], "extra": [ 1, 170, 226, 134, 127, 24, 55, 193, 203, 58, 240, 12, 147, 48, 244, 161, 41, 230, 141, 110, 42, 129, 75, 216, 26, 163, 119, 22, 227, 8, 61, 146, 21, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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