Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f42aa1c1c392676e5946cdff7b02fb32fcc61aa5b6c82d21a17c3709138b2c9

Tx prefix hash: 95745ef0e6d55f897627a0d81e0997814e06bd16ac62530215931a3e0d2a6a30
Tx public key: 52fb3ef6c297f2820a0b5953521245a67f8b43fd0462b6da83625070e33eadc0
Timestamp: 1711955311 Timestamp [UCT]: 2024-04-01 07:08:31 Age [y:d:h:m:s]: 00:298:16:03:45
Block: 990826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213769 RingCT/type: yes/0
Extra: 0152fb3ef6c297f2820a0b5953521245a67f8b43fd0462b6da83625070e33eadc002110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22cccfde643467fd83dd5ca7b52f3f79d45703054543d50424f9048babb66208 0.600000000000 1451156 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": 990836, "vin": [ { "gen": { "height": 990826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22cccfde643467fd83dd5ca7b52f3f79d45703054543d50424f9048babb66208" } } ], "extra": [ 1, 82, 251, 62, 246, 194, 151, 242, 130, 10, 11, 89, 83, 82, 18, 69, 166, 127, 139, 67, 253, 4, 98, 182, 218, 131, 98, 80, 112, 227, 62, 173, 192, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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