Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ec6ae93403ebefc11c0cb72765b018a88f53a77dcbfc3f13d4f2e726f49647b

Tx prefix hash: 9f678d12ff1e1c855590d5cf3ba964b717c34c352a5c7fc569bf1fbbd663e155
Tx public key: 86dd52333cf4420feb77f202a203db14d346c289d6b86552ff82510b1f6dad00
Timestamp: 1639252906 Timestamp [UCT]: 2021-12-11 20:01:46 Age [y:d:h:m:s]: 03:324:12:35:48
Block: 393408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1008405 RingCT/type: yes/0
Extra: 0186dd52333cf4420feb77f202a203db14d346c289d6b86552ff82510b1f6dad0002110000000176899486000000000000000000

1 output(s) for total of 30.512398353000 dcy

stealth address amount amount idx
00: 5780f4e0c0b5b5b39adf2d4805999f8dc3ad86906a533ad31e9babd15d9a04f6 30.512398353000 790637 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": 393418, "vin": [ { "gen": { "height": 393408 } } ], "vout": [ { "amount": 30512398353, "target": { "key": "5780f4e0c0b5b5b39adf2d4805999f8dc3ad86906a533ad31e9babd15d9a04f6" } } ], "extra": [ 1, 134, 221, 82, 51, 60, 244, 66, 15, 235, 119, 242, 2, 162, 3, 219, 20, 211, 70, 194, 137, 214, 184, 101, 82, 255, 130, 81, 11, 31, 109, 173, 0, 2, 17, 0, 0, 0, 1, 118, 137, 148, 134, 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