Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2600945ef64a645197a87b3100d14e6737af0e3a7b797b9e2f88b15383349f9

Tx prefix hash: 68e0b8f531c995efc72eb691b77c2e01f1a26c8948d7d5da29a4642cf74214ac
Tx public key: 4d7674fa97b89d75686234ba00e14f03f2a5e8740767974e614b10d22df01afb
Timestamp: 1716967693 Timestamp [UCT]: 2024-05-29 07:28:13 Age [y:d:h:m:s]: 00:155:06:06:35
Block: 1032416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111139 RingCT/type: yes/0
Extra: 014d7674fa97b89d75686234ba00e14f03f2a5e8740767974e614b10d22df01afb02110000000341ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69b53a62d69bd28225b40e180d879ab6384bafe9abb9f0ebf371aa994ce4ed4e 0.600000000000 1500869 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": 1032426, "vin": [ { "gen": { "height": 1032416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69b53a62d69bd28225b40e180d879ab6384bafe9abb9f0ebf371aa994ce4ed4e" } } ], "extra": [ 1, 77, 118, 116, 250, 151, 184, 157, 117, 104, 98, 52, 186, 0, 225, 79, 3, 242, 165, 232, 116, 7, 103, 151, 78, 97, 75, 16, 210, 45, 240, 26, 251, 2, 17, 0, 0, 0, 3, 65, 238, 28, 155, 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