Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef6f11e79dd22fd195b8c6467d1722ce753281451f60c2170926fca31e45973a

Tx prefix hash: cf4b52f34d6b1121f8c7010b2c70d82036e646f40a0b3d4708d347898218641c
Tx public key: c0a84d5571dc72263e80d85448e6fbfea2fe771c59ac9b5b5548c1b6a4a5cf55
Timestamp: 1578439527 Timestamp [UCT]: 2020-01-07 23:25:27 Age [y:d:h:m:s]: 05:114:08:00:38
Block: 40847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1231732 RingCT/type: yes/0
Extra: 01c0a84d5571dc72263e80d85448e6fbfea2fe771c59ac9b5b5548c1b6a4a5cf5502110000003417786bcf000000000000000000

1 output(s) for total of 449.445291129000 dcy

stealth address amount amount idx
00: 401b34a87496b7fc9ecf0f109698e51644046be2bc27dbd5fb3b8a995c1e679b 449.445291129000 72143 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": 40857, "vin": [ { "gen": { "height": 40847 } } ], "vout": [ { "amount": 449445291129, "target": { "key": "401b34a87496b7fc9ecf0f109698e51644046be2bc27dbd5fb3b8a995c1e679b" } } ], "extra": [ 1, 192, 168, 77, 85, 113, 220, 114, 38, 62, 128, 216, 84, 72, 230, 251, 254, 162, 254, 119, 28, 89, 172, 155, 91, 85, 72, 193, 182, 164, 165, 207, 85, 2, 17, 0, 0, 0, 52, 23, 120, 107, 207, 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