Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 798f609f038fffa1b5a1038d2a879b1624528ee85ff1bc2000a9a22e01a6edbc

Tx prefix hash: 6269c6b6834814353d17e96e286e365cb875802f782036a2fb3f035561fcf2e1
Tx public key: e2ea1ca6b021a579b8a7d281c17b118eb665fbabf3ad44fdaf9ce8ddc7a1b2ec
Timestamp: 1578801363 Timestamp [UCT]: 2020-01-12 03:56:03 Age [y:d:h:m:s]: 05:272:02:35:00
Block: 43628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1342368 RingCT/type: yes/0
Extra: 01e2ea1ca6b021a579b8a7d281c17b118eb665fbabf3ad44fdaf9ce8ddc7a1b2ec0211000000114ac5aa02000000000000000000

1 output(s) for total of 439.990366169000 dcy

stealth address amount amount idx
00: b4d13b99cefa08c48a1314e8ef01e741348649d29e69b79282b4ce03e99e38c1 439.990366169000 79102 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": 43638, "vin": [ { "gen": { "height": 43628 } } ], "vout": [ { "amount": 439990366169, "target": { "key": "b4d13b99cefa08c48a1314e8ef01e741348649d29e69b79282b4ce03e99e38c1" } } ], "extra": [ 1, 226, 234, 28, 166, 176, 33, 165, 121, 184, 167, 210, 129, 193, 123, 17, 142, 182, 101, 251, 171, 243, 173, 68, 253, 175, 156, 232, 221, 199, 161, 178, 236, 2, 17, 0, 0, 0, 17, 74, 197, 170, 2, 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