Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f41ef4e7b2ead72aa25132510eab9a894330ce9e4731b9dcf61ec91e2b7f987a

Tx prefix hash: d044a65172813ce3aba995bd07fa230f4da2c6d84ddd249e03ae1f788f2bc9e6
Tx public key: 859436a72e6079c747d048e7518c7196b0c5c35e3b33da220d457849b023afaf
Timestamp: 1716559291 Timestamp [UCT]: 2024-05-24 14:01:31 Age [y:d:h:m:s]: 00:233:11:25:36
Block: 1029038 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167086 RingCT/type: yes/0
Extra: 01859436a72e6079c747d048e7518c7196b0c5c35e3b33da220d457849b023afaf0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3961712dd92505787d0d490c7f96d5cc62b0e70b5ab36302a542de3b5e5874b7 0.600000000000 1497039 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": 1029048, "vin": [ { "gen": { "height": 1029038 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3961712dd92505787d0d490c7f96d5cc62b0e70b5ab36302a542de3b5e5874b7" } } ], "extra": [ 1, 133, 148, 54, 167, 46, 96, 121, 199, 71, 208, 72, 231, 81, 140, 113, 150, 176, 197, 195, 94, 59, 51, 218, 34, 13, 69, 120, 73, 176, 35, 175, 175, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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