Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff645b83fb1cca858491bb1f72cb3506d79d6ac3b702a3a1e2f74bd955085945

Tx prefix hash: c3ec177fbf96862bdf416c5bca645ea44c52e5df818d6b45f9963be6b30a71f9
Tx public key: 1d45d73ca0d1ee8645f200d0e1eaef05fc992f11f1bd73c690de433b357cb070
Timestamp: 1583451701 Timestamp [UCT]: 2020-03-05 23:41:41 Age [y:d:h:m:s]: 04:297:06:44:04
Block: 77049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1107067 RingCT/type: yes/0
Extra: 011d45d73ca0d1ee8645f200d0e1eaef05fc992f11f1bd73c690de433b357cb070021100000009d81c26c0000000000000000000

1 output(s) for total of 340.969351852000 dcy

stealth address amount amount idx
00: 32e77601dc551fda0a7e6a9f9251e5456604e24536391f68d24179620329cab7 340.969351852000 141869 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": 77059, "vin": [ { "gen": { "height": 77049 } } ], "vout": [ { "amount": 340969351852, "target": { "key": "32e77601dc551fda0a7e6a9f9251e5456604e24536391f68d24179620329cab7" } } ], "extra": [ 1, 29, 69, 215, 60, 160, 209, 238, 134, 69, 242, 0, 208, 225, 234, 239, 5, 252, 153, 47, 17, 241, 189, 115, 198, 144, 222, 67, 59, 53, 124, 176, 112, 2, 17, 0, 0, 0, 9, 216, 28, 38, 192, 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