Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc1f141f2c800cd1f6561ffe1a577e5971b70d66c4da7235e9a5049de90463d6

Tx prefix hash: 434e933a1f4c2ad869cb052d9ee3f38c5f109bca8e42ce38741554778a4dd7da
Tx public key: 3c25279cc21fc397c8e94422476ab27de086e5bdd4fdef2ab895197f8e346abc
Timestamp: 1633182919 Timestamp [UCT]: 2021-10-02 13:55:19 Age [y:d:h:m:s]: 03:223:13:58:10
Block: 345216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 936544 RingCT/type: yes/0
Extra: 013c25279cc21fc397c8e94422476ab27de086e5bdd4fdef2ab895197f8e346abc0211000000165d7cc334000000000000000000

1 output(s) for total of 44.072616136000 dcy

stealth address amount amount idx
00: 6e955f8606a768b3936db4254bc7832295d2727cb9c7687660a54c1c6b221ab3 44.072616136000 708168 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": 345226, "vin": [ { "gen": { "height": 345216 } } ], "vout": [ { "amount": 44072616136, "target": { "key": "6e955f8606a768b3936db4254bc7832295d2727cb9c7687660a54c1c6b221ab3" } } ], "extra": [ 1, 60, 37, 39, 156, 194, 31, 195, 151, 200, 233, 68, 34, 71, 106, 178, 125, 224, 134, 229, 189, 212, 253, 239, 42, 184, 149, 25, 127, 142, 52, 106, 188, 2, 17, 0, 0, 0, 22, 93, 124, 195, 52, 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