Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 342be44da95926a89829ef8be8604952e49e1444df9d10751059f9bc0e414102

Tx prefix hash: 8cabb2ce2e275506f5dc54c110ef6b2a788101c0f79cf14d23fa6d5dc04b7588
Tx public key: 85a1215f4490f8f804ac0575d3b38decacc261fb8a51f529dcda5225406446d4
Timestamp: 1684281666 Timestamp [UCT]: 2023-05-17 00:01:06 Age [y:d:h:m:s]: 02:177:04:44:48
Block: 761689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 646441 RingCT/type: yes/0
Extra: 0185a1215f4490f8f804ac0575d3b38decacc261fb8a51f529dcda5225406446d4021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.837419567000 dcy

stealth address amount amount idx
00: 6aa404b0f4fee36d5899aeee6cd995b67d9aae7ee74b87847de566edab161ff6 1.837419567000 1210376 of 0

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": 761699, "vin": [ { "gen": { "height": 761689 } } ], "vout": [ { "amount": 1837419567, "target": { "key": "6aa404b0f4fee36d5899aeee6cd995b67d9aae7ee74b87847de566edab161ff6" } } ], "extra": [ 1, 133, 161, 33, 95, 68, 144, 248, 248, 4, 172, 5, 117, 211, 179, 141, 236, 172, 194, 97, 251, 138, 81, 245, 41, 220, 218, 82, 37, 64, 100, 70, 212, 2, 17, 0, 0, 0, 1, 230, 210, 127, 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