Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d8b0a390c25253be9bb68d9e65fe9c1402987a4d3fe159bae4a4cedc75afd5f

Tx prefix hash: 6edcaa7f0d4c0b1b9f65dd30721e9bb6d718eb422703edc8ed84f7c5f9b229e1
Tx public key: 5cf370eda790f208b7d7c35909f8c59a55b2a2d3d316c9813430c45393094b82
Timestamp: 1580706020 Timestamp [UCT]: 2020-02-03 05:00:20 Age [y:d:h:m:s]: 04:277:05:45:06
Block: 57783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1089255 RingCT/type: yes/0
Extra: 015cf370eda790f208b7d7c35909f8c59a55b2a2d3d316c9813430c45393094b820211000000158a2ee0d9000000000000000000

1 output(s) for total of 394.985220389000 dcy

stealth address amount amount idx
00: 8a2bb33b0f5c74692e7759d30df3ef23aa8d260c5aebedda166e54c619ed694b 394.985220389000 106781 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": 57793, "vin": [ { "gen": { "height": 57783 } } ], "vout": [ { "amount": 394985220389, "target": { "key": "8a2bb33b0f5c74692e7759d30df3ef23aa8d260c5aebedda166e54c619ed694b" } } ], "extra": [ 1, 92, 243, 112, 237, 167, 144, 242, 8, 183, 215, 195, 89, 9, 248, 197, 154, 85, 178, 162, 211, 211, 22, 201, 129, 52, 48, 196, 83, 147, 9, 75, 130, 2, 17, 0, 0, 0, 21, 138, 46, 224, 217, 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